Utilizing Gateway Channel Resources for SBC

The device can utilize resources of non-configured Gateway channels for SBC sessions, regardless of whether the device is licensed for SBC functionality. This feature, in essence, allows "call" resources to be migrated from the Gateway application to the SBC application, allowing you to migrate your Gateway deployment to an all IP-based voice network with only a simple configuration change. One of the main advantages of the feature is that if you purchased the device for deploying it initially as a Gateway for PSTN calls, you can at any stage easily use the device for SBC calls without having to purchase an SBC license.

A Gateway channel is considered "not configured" if it is not associated with any Trunk Group (see Configuring Trunk Groups). If all Gateway channels are configured, resources from these channels cannot be used for SBC sessions. If the resources of a currently active SBC call is obtained from a Gateway channel and you configure all Gateway channels during the call, the device maintains the SBC call until it is terminated by the call parties, but obtaining resources from Gateway channels for new SBC calls will not be made possible.

For every non-configured Gateway channel, one SBC session can be processed. For example:

A License Key licensing 4 FXS can support up to 4 SBC sessions (4 channels for FXS port) if all the Gateway channels are not configured. If the License Key also provides a license for 5 SBC sessions, up to 9 SBC sessions (4 channels for FXS + 5 sessions for SBC) can be supported.

The number of SBC sessions that can be derived from using resources from Gateway channels that are not configured is displayed in the Web interface's License Key page (see Viewing the License Key), in the 'TDM-to-SBC Sessions' field.